Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bf78bc9cd63aff7f1a49212e267aff47a2689f7098834a2848d145e8f9a491b

Tx prefix hash: d3ecd824713cfdb8834334843d120a383fca2132f565164bfd703fea6e182a5e
Tx public key: 43868be91a2a455a83e4e3ed5d4977125d0aac5eeaa03d556d83ec7cce8603fb
Timestamp: 1578242764 Timestamp [UCT]: 2020-01-05 16:46:04 Age [y:d:h:m:s]: 04:359:04:25:40
Block: 39324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1145941 RingCT/type: yes/0
Extra: 0143868be91a2a455a83e4e3ed5d4977125d0aac5eeaa03d556d83ec7cce8603fb0211000000c72264afe6000000000000000000

1 output(s) for total of 454.686019515000 dcy

stealth address amount amount idx
00: 811e169f8b42044b88b28b6d6d6afb8f15e17deadddb7508d379367700f55230 454.686019515000 67734 of 0

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": 39334, "vin": [ { "gen": { "height": 39324 } } ], "vout": [ { "amount": 454686019515, "target": { "key": "811e169f8b42044b88b28b6d6d6afb8f15e17deadddb7508d379367700f55230" } } ], "extra": [ 1, 67, 134, 139, 233, 26, 42, 69, 90, 131, 228, 227, 237, 93, 73, 119, 18, 93, 10, 172, 94, 234, 160, 61, 85, 109, 131, 236, 124, 206, 134, 3, 251, 2, 17, 0, 0, 0, 199, 34, 100, 175, 230, 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