Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff0212a0efe96a5593fdd2de6b15a761c6de3a415d2be70a768262b41b77af04

Tx prefix hash: 5b27deedf65a9080f7aa9aafbe04bc8bec0f09f70ebb62cf25213991fdfb76cc
Tx public key: 2687522c73ce6294a39265acc0622933581c2ba5fe9e34f81beef79f38b93fb2
Timestamp: 1724667510 Timestamp [UCT]: 2024-08-26 10:18:30 Age [y:d:h:m:s]: 00:208:23:13:53
Block: 1096245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149213 RingCT/type: yes/0
Extra: 012687522c73ce6294a39265acc0622933581c2ba5fe9e34f81beef79f38b93fb2021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e7e654df76cdee8b3b784888dee2fe6a15f2e2ac61c5c05b329165731f42c47 0.600000000000 1571432 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": 1096255, "vin": [ { "gen": { "height": 1096245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e7e654df76cdee8b3b784888dee2fe6a15f2e2ac61c5c05b329165731f42c47" } } ], "extra": [ 1, 38, 135, 82, 44, 115, 206, 98, 148, 163, 146, 101, 172, 192, 98, 41, 51, 88, 28, 43, 165, 254, 158, 52, 248, 27, 238, 247, 159, 56, 185, 63, 178, 2, 17, 0, 0, 0, 7, 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