Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 416b47e62dd5ad84d53d05d7087b942cf2301d5e00b645ea2aaaa72751fe1b53

Tx prefix hash: bbdc224af29bab232a9057aec7093aadd55d94593e1684f1356e213cad9997b4
Tx public key: 9efd80a1ac8223aea67b96f11140f175672e1d710dbd9a2e8af1ab8126939ebd
Timestamp: 1704609340 Timestamp [UCT]: 2024-01-07 06:35:40 Age [y:d:h:m:s]: 01:017:08:57:04
Block: 929931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273730 RingCT/type: yes/0
Extra: 019efd80a1ac8223aea67b96f11140f175672e1d710dbd9a2e8af1ab8126939ebd0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7d5bb2bb14c508c1346b1c64c2238b512ad63c0b9b3085e7bd2be7f871368d9 0.600000000000 1387809 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": 929941, "vin": [ { "gen": { "height": 929931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7d5bb2bb14c508c1346b1c64c2238b512ad63c0b9b3085e7bd2be7f871368d9" } } ], "extra": [ 1, 158, 253, 128, 161, 172, 130, 35, 174, 166, 123, 150, 241, 17, 64, 241, 117, 103, 46, 29, 113, 13, 189, 154, 46, 138, 241, 171, 129, 38, 147, 158, 189, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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