Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a34cffd748e8977e509e32af71a2cbde7bd2ec2946c11718fbbb7bbdf9fca4f9

Tx prefix hash: 2863bcaf6733cba5cf95f84407b2e384ebc3a7ea1ffe68281e0df93067151864
Tx public key: 25e3822af8ea94a274513d3e36a6a817f4c44d029c1cfad05864efbaa876006d
Timestamp: 1729519039 Timestamp [UCT]: 2024-10-21 13:57:19 Age [y:d:h:m:s]: 00:033:14:04:56
Block: 1136429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24003 RingCT/type: yes/0
Extra: 0125e3822af8ea94a274513d3e36a6a817f4c44d029c1cfad05864efbaa876006d021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6ba4766271aeabade8bf097025424cb005883e094be3da9bc043c35359e7f63 0.600000000000 1619774 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": 1136439, "vin": [ { "gen": { "height": 1136429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6ba4766271aeabade8bf097025424cb005883e094be3da9bc043c35359e7f63" } } ], "extra": [ 1, 37, 227, 130, 42, 248, 234, 148, 162, 116, 81, 61, 62, 54, 166, 168, 23, 244, 196, 77, 2, 156, 28, 250, 208, 88, 100, 239, 186, 168, 118, 0, 109, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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