Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce8f7885263eee029ec890e684ead604d6077077da7b26cb48e3fd4c3170703a

Tx prefix hash: df35e386c3178eaeacd40fb99586515507ecb1fc0278ca01bbcfc738e75ed84f
Tx public key: a3e338b868e013b8c57776d4e1642733b056a6107c7df9581c12b844de0ea52c
Timestamp: 1704611546 Timestamp [UCT]: 2024-01-07 07:12:26 Age [y:d:h:m:s]: 01:072:16:23:34
Block: 929954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313083 RingCT/type: yes/0
Extra: 01a3e338b868e013b8c57776d4e1642733b056a6107c7df9581c12b844de0ea52c0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb3c081ba81409a48e0ae7c50ff739a49c4eabbe582d4e7d21b4d90caf800a2f 0.600000000000 1387832 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": 929964, "vin": [ { "gen": { "height": 929954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb3c081ba81409a48e0ae7c50ff739a49c4eabbe582d4e7d21b4d90caf800a2f" } } ], "extra": [ 1, 163, 227, 56, 184, 104, 224, 19, 184, 197, 119, 118, 212, 225, 100, 39, 51, 176, 86, 166, 16, 124, 125, 249, 88, 28, 18, 184, 68, 222, 14, 165, 44, 2, 17, 0, 0, 0, 1, 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