Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f36c7bc864dabb5228a38aaf535a0d700a96878858cd4d820471fc5626cb714

Tx prefix hash: e23766e6b0a04ab5665843a58f1071b1e62aebd5794681f5ec75e9c7d0b0e2f1
Tx public key: 38bf2038748f7a6c1e873e8c447c851e34f464fd2185b68a3d952c716daae97f
Timestamp: 1717735266 Timestamp [UCT]: 2024-06-07 04:41:06 Age [y:d:h:m:s]: 00:229:08:53:15
Block: 1038782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164106 RingCT/type: yes/0
Extra: 0138bf2038748f7a6c1e873e8c447c851e34f464fd2185b68a3d952c716daae97f0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50e9f8543e3bd7e6d59ed1ad9c0f231ee7d21b606609dbbd4093e63fc94db2c5 0.600000000000 1507343 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": 1038792, "vin": [ { "gen": { "height": 1038782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50e9f8543e3bd7e6d59ed1ad9c0f231ee7d21b606609dbbd4093e63fc94db2c5" } } ], "extra": [ 1, 56, 191, 32, 56, 116, 143, 122, 108, 30, 135, 62, 140, 68, 124, 133, 30, 52, 244, 100, 253, 33, 133, 182, 138, 61, 149, 44, 113, 109, 170, 233, 127, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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