Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21a1c6d2e61a02abb91c34d925c35507a9c12516755f5cb1af25ea8724cf2104

Tx prefix hash: 0ce08099bece2ac651141afec1f807be5c51ccd67a3a149198610d54010e41e9
Tx public key: 5ce2139b6b3c2731b3c4d68ee9648b070d275780b376ce2afa3f51d176062a9c
Timestamp: 1717220671 Timestamp [UCT]: 2024-06-01 05:44:31 Age [y:d:h:m:s]: 00:349:23:32:05
Block: 1034519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250145 RingCT/type: yes/0
Extra: 015ce2139b6b3c2731b3c4d68ee9648b070d275780b376ce2afa3f51d176062a9c0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a196b059c456341f2a8102fd6aadcd2063efe4b9cd8e7f9b36546fb4c677b49 0.600000000000 1503032 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": 1034529, "vin": [ { "gen": { "height": 1034519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a196b059c456341f2a8102fd6aadcd2063efe4b9cd8e7f9b36546fb4c677b49" } } ], "extra": [ 1, 92, 226, 19, 155, 107, 60, 39, 49, 179, 196, 214, 142, 233, 100, 139, 7, 13, 39, 87, 128, 179, 118, 206, 42, 250, 63, 81, 209, 118, 6, 42, 156, 2, 17, 0, 0, 0, 2, 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