Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b0aa84d18a9b463069e34b7316c71442ca953767f615bcd2def965a96ad2b1b6

Tx prefix hash: aecd42b8ba73aa0bc8cfab3c9789fae8bc94bc50ee2ecc0538bf6ca882900aa8
Tx public key: f002557a33a6af543f594ccf87e952a1b193bc0f534c680329d09fc7739c2cb8
Timestamp: 1717384196 Timestamp [UCT]: 2024-06-03 03:09:56 Age [y:d:h:m:s]: 00:296:01:48:45
Block: 1035883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211564 RingCT/type: yes/0
Extra: 01f002557a33a6af543f594ccf87e952a1b193bc0f534c680329d09fc7739c2cb8021100000001162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8653f20121f6b99046cbe4a3352f26e5733f25e57b7226020a2805841a2d7b8 0.600000000000 1504406 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1035893, "vin": [ { "gen": { "height": 1035883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8653f20121f6b99046cbe4a3352f26e5733f25e57b7226020a2805841a2d7b8" } } ], "extra": [ 1, 240, 2, 85, 122, 51, 166, 175, 84, 63, 89, 76, 207, 135, 233, 82, 161, 177, 147, 188, 15, 83, 76, 104, 3, 41, 208, 159, 199, 115, 156, 44, 184, 2, 17, 0, 0, 0, 1, 22, 38, 19, 170, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8