Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cff7f5fcb351d7a0c53f8021f81fb984aa41ca00e7a9189f876a33388aa7e33d

Tx prefix hash: bbc09b0048ba1898eae66734d234b08ae46419506dcb2d67a5e104aae590cf19
Tx public key: 6813b3d5ec7e6c36e5c142231413b3eaf0c56ddefbacff81efb23580745e4c31
Timestamp: 1718456457 Timestamp [UCT]: 2024-06-15 13:00:57 Age [y:d:h:m:s]: 00:226:06:39:36
Block: 1044772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161664 RingCT/type: yes/0
Extra: 016813b3d5ec7e6c36e5c142231413b3eaf0c56ddefbacff81efb23580745e4c310211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0d310b4dd5b211f88f8f368f504a6e62b9617de33e4cef353f773972a15dd03 0.600000000000 1514169 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": 1044782, "vin": [ { "gen": { "height": 1044772 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0d310b4dd5b211f88f8f368f504a6e62b9617de33e4cef353f773972a15dd03" } } ], "extra": [ 1, 104, 19, 179, 213, 236, 126, 108, 54, 229, 193, 66, 35, 20, 19, 179, 234, 240, 197, 109, 222, 251, 172, 255, 129, 239, 178, 53, 128, 116, 94, 76, 49, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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