Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a632a68d87383fb1255261863a903c403b5c5d923a9293408cd85875d00ed219

Tx prefix hash: 0ef5fc2987a8d9f4393a74ad8e65e9702b63e0b918dc562683af90930a1355b2
Tx public key: f994eeb7080311920b02f3df114bf861cbb969a929c84e2a2fe1a013181714a6
Timestamp: 1709391858 Timestamp [UCT]: 2024-03-02 15:04:18 Age [y:d:h:m:s]: 00:334:03:25:50
Block: 969614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238921 RingCT/type: yes/0
Extra: 01f994eeb7080311920b02f3df114bf861cbb969a929c84e2a2fe1a013181714a602110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d04192a8a45d3b4bd8fd164c35936a21cb37b6e50865109886aee40dd986de7 0.600000000000 1429451 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": 969624, "vin": [ { "gen": { "height": 969614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d04192a8a45d3b4bd8fd164c35936a21cb37b6e50865109886aee40dd986de7" } } ], "extra": [ 1, 249, 148, 238, 183, 8, 3, 17, 146, 11, 2, 243, 223, 17, 75, 248, 97, 203, 185, 105, 169, 41, 200, 78, 42, 47, 225, 160, 19, 24, 23, 20, 166, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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