Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bec173b66bfd417964c5e27cd23fec28fea2df5a8e70ea4d061dba44b60fe450

Tx prefix hash: 705d537ce07c54e6d2a2f1608cd30e49b5f92cb10633e53869037fc3ffd0531f
Tx public key: da59d0df055262adb4d98b46cc107e91c44fca920115ef597b48f6837f1c9ece
Timestamp: 1574132016 Timestamp [UCT]: 2019-11-19 02:53:36 Age [y:d:h:m:s]: 05:082:22:51:21
Block: 12371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1202099 RingCT/type: yes/0
Extra: 01da59d0df055262adb4d98b46cc107e91c44fca920115ef597b48f6837f1c9ece02110000000466a80d00000000000000000000

1 output(s) for total of 558.483863724000 dcy

stealth address amount amount idx
00: 8033ba629be0d9f9fc681dbf2aadfbc8b7f68da8a6e4ad60f6a37ed55f4283a1 558.483863724000 13588 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": 12381, "vin": [ { "gen": { "height": 12371 } } ], "vout": [ { "amount": 558483863724, "target": { "key": "8033ba629be0d9f9fc681dbf2aadfbc8b7f68da8a6e4ad60f6a37ed55f4283a1" } } ], "extra": [ 1, 218, 89, 208, 223, 5, 82, 98, 173, 180, 217, 139, 70, 204, 16, 126, 145, 196, 79, 202, 146, 1, 21, 239, 89, 123, 72, 246, 131, 127, 28, 158, 206, 2, 17, 0, 0, 0, 4, 102, 168, 13, 0, 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