Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5a40ab775386e7d8d4ba34df657b4c872592f3a402d5a89c57570611979a483

Tx prefix hash: 43bcf4dd64275e822935239d4a126cfa4008c9bc18c529be12b1b684861dd2bc
Tx public key: 84a6d9f5e68ef2df1b4d0310ae212f2212094cb4a381f9e5e49001e4a0c49136
Timestamp: 1730467141 Timestamp [UCT]: 2024-11-01 13:19:01 Age [y:d:h:m:s]: 00:065:22:07:37
Block: 1144250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47182 RingCT/type: yes/0
Extra: 0184a6d9f5e68ef2df1b4d0310ae212f2212094cb4a381f9e5e49001e4a0c491360211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc5bd6b977ad6e272d39365eb1532abee9c0d162f6d4db277bca4ab0cf1fa3e0 0.600000000000 1628405 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": 1144260, "vin": [ { "gen": { "height": 1144250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc5bd6b977ad6e272d39365eb1532abee9c0d162f6d4db277bca4ab0cf1fa3e0" } } ], "extra": [ 1, 132, 166, 217, 245, 230, 142, 242, 223, 27, 77, 3, 16, 174, 33, 47, 34, 18, 9, 76, 180, 163, 129, 249, 229, 228, 144, 1, 228, 160, 196, 145, 54, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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