Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f7d239ecc9c15fcf324f0331f14a5a2557dcf4bdc808716b607f4ff1d9a14b9

Tx prefix hash: feb96c9bd7458e7034a19f7bdf34df40d306d67bba0556bc32442e02e6ceb994
Tx public key: 7ac47323d0372aed915b5a548be1157a2ecdefe21c37fc4e2585f16cfe4056c1
Timestamp: 1644561359 Timestamp [UCT]: 2022-02-11 06:35:59 Age [y:d:h:m:s]: 03:078:04:52:09
Block: 436131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 835858 RingCT/type: yes/0
Extra: 017ac47323d0372aed915b5a548be1157a2ecdefe21c37fc4e2585f16cfe4056c10211000000085eb576c5000000000000000000

1 output(s) for total of 22.025067573000 dcy

stealth address amount amount idx
00: 4d19870d657529d6ebef213f62bdb3d7ea89158258ba2676a9b7565197200497 22.025067573000 847448 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": 436141, "vin": [ { "gen": { "height": 436131 } } ], "vout": [ { "amount": 22025067573, "target": { "key": "4d19870d657529d6ebef213f62bdb3d7ea89158258ba2676a9b7565197200497" } } ], "extra": [ 1, 122, 196, 115, 35, 208, 55, 42, 237, 145, 91, 90, 84, 139, 225, 21, 122, 46, 205, 239, 226, 28, 55, 252, 78, 37, 133, 241, 108, 254, 64, 86, 193, 2, 17, 0, 0, 0, 8, 94, 181, 118, 197, 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