Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72b78cc909604cbc394444f779c3cc78d799d6600a2e477d20962137d06d53b4

Tx prefix hash: 813a4734f6869fec6eba05e7fd9d7bdf84e59e9fd4037bf9b1c3aff559f53ff4
Tx public key: dcac038ced8117eb6b0407648d3b9800d3bbacf50b10c8d7ee028c08f7e7fefa
Timestamp: 1698636420 Timestamp [UCT]: 2023-10-30 03:27:00 Age [y:d:h:m:s]: 01:074:11:21:04
Block: 880655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314441 RingCT/type: yes/0
Extra: 01dcac038ced8117eb6b0407648d3b9800d3bbacf50b10c8d7ee028c08f7e7fefa021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.741351925000 dcy

stealth address amount amount idx
00: d472ed8c9c4214086cf362145f5319e0dbd353b51933516096e351752cc38512 0.741351925000 1336219 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": 880665, "vin": [ { "gen": { "height": 880655 } } ], "vout": [ { "amount": 741351925, "target": { "key": "d472ed8c9c4214086cf362145f5319e0dbd353b51933516096e351752cc38512" } } ], "extra": [ 1, 220, 172, 3, 140, 237, 129, 23, 235, 107, 4, 7, 100, 141, 59, 152, 0, 211, 187, 172, 245, 11, 16, 200, 215, 238, 2, 140, 8, 247, 231, 254, 250, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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