Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f801dce2f20fab9e655d89892e62e4c51962b39b79f725301f11d827b966fbe1

Tx prefix hash: 3feb230c25c40dc2eaa98069883185423fd194ce4026b425d231761472442bce
Tx public key: 6a4e32eb2c804e85c8a5d4d58dfb2d6ca2a499680ddc2c8c8c1a17bff0ed54cd
Timestamp: 1717909625 Timestamp [UCT]: 2024-06-09 05:07:05 Age [y:d:h:m:s]: 00:323:11:43:05
Block: 1040222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231204 RingCT/type: yes/0
Extra: 016a4e32eb2c804e85c8a5d4d58dfb2d6ca2a499680ddc2c8c8c1a17bff0ed54cd02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a90d0dca29cdb40302554c01bd6f6fc837e0f4b697d0643b11169900b684f4e 0.600000000000 1508879 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": 1040232, "vin": [ { "gen": { "height": 1040222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a90d0dca29cdb40302554c01bd6f6fc837e0f4b697d0643b11169900b684f4e" } } ], "extra": [ 1, 106, 78, 50, 235, 44, 128, 78, 133, 200, 165, 212, 213, 141, 251, 45, 108, 162, 164, 153, 104, 13, 220, 44, 140, 140, 26, 23, 191, 240, 237, 84, 205, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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