Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64c930aa0d1a97c8796c080ce2bc6d55f2fa9134c5be8e5307bc931b8861a221

Tx prefix hash: f2e683866403522651e8a526c2f451236389b3ed7e1ab4e41a7e1f869e20f8e3
Tx public key: 3527fb4f8f15d5839d3e76bdd240b99686618d3d355131dbe0097bc0e90eba3c
Timestamp: 1580791258 Timestamp [UCT]: 2020-02-04 04:40:58 Age [y:d:h:m:s]: 05:248:21:21:18
Block: 58295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1327559 RingCT/type: yes/0
Extra: 013527fb4f8f15d5839d3e76bdd240b99686618d3d355131dbe0097bc0e90eba3c021100000003dcee4b4d000000000000000000

1 output(s) for total of 393.409901684000 dcy

stealth address amount amount idx
00: 2dcdcf614c64ccfeefa514d3ad112e848cdac822bc8151e10adc9be092e8f1b4 393.409901684000 107729 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": 58305, "vin": [ { "gen": { "height": 58295 } } ], "vout": [ { "amount": 393409901684, "target": { "key": "2dcdcf614c64ccfeefa514d3ad112e848cdac822bc8151e10adc9be092e8f1b4" } } ], "extra": [ 1, 53, 39, 251, 79, 143, 21, 213, 131, 157, 62, 118, 189, 210, 64, 185, 150, 134, 97, 141, 61, 53, 81, 49, 219, 224, 9, 123, 192, 233, 14, 186, 60, 2, 17, 0, 0, 0, 3, 220, 238, 75, 77, 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