Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2a546e922d64f6b79164c83cd543af2cd00f4317bb30f7ace4a2d71e4e798f8

Tx prefix hash: 8147ec3c463ef66c326b10f8c2db796b9f2f03c8ded5f848f1bf3a8012d04dcb
Tx public key: e7ae4f33ad9eb754c1fa85ef8788accce679df83df30489f63d24467dbe3d064
Timestamp: 1749672351 Timestamp [UCT]: 2025-06-11 20:05:51 Age [y:d:h:m:s]: 00:153:13:45:45
Block: 1302978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107454 RingCT/type: yes/0
Extra: 01e7ae4f33ad9eb754c1fa85ef8788accce679df83df30489f63d24467dbe3d06402110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccbcaa26a4befb52a1226476d935c027df5a0ba8770eaf55879ad32e18a07c8e 0.600000000000 1790553 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": 1302988, "vin": [ { "gen": { "height": 1302978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccbcaa26a4befb52a1226476d935c027df5a0ba8770eaf55879ad32e18a07c8e" } } ], "extra": [ 1, 231, 174, 79, 51, 173, 158, 183, 84, 193, 250, 133, 239, 135, 136, 172, 204, 230, 121, 223, 131, 223, 48, 72, 159, 99, 210, 68, 103, 219, 227, 208, 100, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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