Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc5fc00158c9b0d4f26516d7ae7acad62381233cfa2f7aa06100f4efda4f10ce

Tx prefix hash: 35c0b46b46bb7eee9174d6901621b836cdc9ac114fccccb18a3b2d539a607710
Tx public key: add6a4f55c0eb4b8f0139007da287a524e42985b56a5e8598d486bdb737e98cb
Timestamp: 1707455571 Timestamp [UCT]: 2024-02-09 05:12:51 Age [y:d:h:m:s]: 01:056:10:50:29
Block: 953549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301395 RingCT/type: yes/0
Extra: 01add6a4f55c0eb4b8f0139007da287a524e42985b56a5e8598d486bdb737e98cb02110000000152d47e94000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: 7663332e3e70ad56f43216c114667d46b9f62edaea2af783310df9977b59307c 0.600010000000 1412773 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": 953559, "vin": [ { "gen": { "height": 953549 } } ], "vout": [ { "amount": 600010000, "target": { "key": "7663332e3e70ad56f43216c114667d46b9f62edaea2af783310df9977b59307c" } } ], "extra": [ 1, 173, 214, 164, 245, 92, 14, 180, 184, 240, 19, 144, 7, 218, 40, 122, 82, 78, 66, 152, 91, 86, 165, 232, 89, 141, 72, 107, 219, 115, 126, 152, 203, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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