Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19dbf17f541b712c6240e9edb8a95b78680f768c423b8e3b2952ad64d5865373

Tx prefix hash: 71ef20dd5aa838d98de118928345aede2e84b6ca8afbad56f95874c028d2f8bb
Tx public key: c546dcad1a1ff847428de877e6124f8a649ddfeb273623d389ea3f4eb4dea55c
Timestamp: 1710674191 Timestamp [UCT]: 2024-03-17 11:16:31 Age [y:d:h:m:s]: 01:017:09:02:33
Block: 980257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273377 RingCT/type: yes/0
Extra: 01c546dcad1a1ff847428de877e6124f8a649ddfeb273623d389ea3f4eb4dea55c0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04a014f25818f00f98ebfc31a7c0c3cdce40a58634906d3a3bd0e7d754a291e9 0.600000000000 1440322 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": 980267, "vin": [ { "gen": { "height": 980257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04a014f25818f00f98ebfc31a7c0c3cdce40a58634906d3a3bd0e7d754a291e9" } } ], "extra": [ 1, 197, 70, 220, 173, 26, 31, 248, 71, 66, 141, 232, 119, 230, 18, 79, 138, 100, 157, 223, 235, 39, 54, 35, 211, 137, 234, 63, 78, 180, 222, 165, 92, 2, 17, 0, 0, 0, 2, 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