Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f816b5754edff5b714066989560c13ae9d66802932fb55bea5c5feaead7ca507

Tx prefix hash: f460e30ff6aba00833273ef022ce60b89402a771555f484116e3eb15cfb62d95
Tx public key: 1042c645e0f29e1b1015b2b038ac7909d8a2f27db12f2a3d5c1b7c50905b3cfd
Timestamp: 1720514659 Timestamp [UCT]: 2024-07-09 08:44:19 Age [y:d:h:m:s]: 00:259:20:39:57
Block: 1061823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185643 RingCT/type: yes/0
Extra: 011042c645e0f29e1b1015b2b038ac7909d8a2f27db12f2a3d5c1b7c50905b3cfd021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a759da4d82fbc7278172da0333286675f6c3524ed02efbce4cfcc36af5547a4 0.600000000000 1532318 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": 1061833, "vin": [ { "gen": { "height": 1061823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a759da4d82fbc7278172da0333286675f6c3524ed02efbce4cfcc36af5547a4" } } ], "extra": [ 1, 16, 66, 198, 69, 224, 242, 158, 27, 16, 21, 178, 176, 56, 172, 121, 9, 216, 162, 242, 125, 177, 47, 42, 61, 92, 27, 124, 80, 144, 91, 60, 253, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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