Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fb57e2b942134d6937ca0d9aa276be9340d314094a799f16b3dc7594dde1485

Tx prefix hash: ef085c760fe8da8076ddf146dfeec52ffb55764b23b1305075a2f95481797cd9
Tx public key: 7060a3511422bb5fee14d07e7e19d28f86690983e5b93f5d88a8addcea22d2e4
Timestamp: 1727484732 Timestamp [UCT]: 2024-09-28 00:52:12 Age [y:d:h:m:s]: 00:212:13:38:18
Block: 1119607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151755 RingCT/type: yes/0
Extra: 017060a3511422bb5fee14d07e7e19d28f86690983e5b93f5d88a8addcea22d2e402110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c95c7a2c6f28f9cbfee5fd9b52d7bd74f24a6819931d42617aa40127fb1ff771 0.600000000000 1601226 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": 1119617, "vin": [ { "gen": { "height": 1119607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c95c7a2c6f28f9cbfee5fd9b52d7bd74f24a6819931d42617aa40127fb1ff771" } } ], "extra": [ 1, 112, 96, 163, 81, 20, 34, 187, 95, 238, 20, 208, 126, 126, 25, 210, 143, 134, 105, 9, 131, 229, 185, 63, 93, 136, 168, 173, 220, 234, 34, 210, 228, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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