Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7537747e30c1589c4350bd5a89339b21543eb4b1459625611f394a8dbb164c7d

Tx prefix hash: 4b551318fb7aae6664e0ea697bc481de56c4d8f11c13fc382e244dfd24de4e06
Tx public key: a849391bc03cba651c8afbf09de8886f7fb3e875a56ce28de85a1065d3ad6dc4
Timestamp: 1721746946 Timestamp [UCT]: 2024-07-23 15:02:26 Age [y:d:h:m:s]: 00:275:10:23:56
Block: 1072029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196791 RingCT/type: yes/0
Extra: 01a849391bc03cba651c8afbf09de8886f7fb3e875a56ce28de85a1065d3ad6dc4021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7da2f4cc9305d18302e7a092de318474ed6b8ea9f0c94e11c612e0216b4afc98 0.600000000000 1544456 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": 1072039, "vin": [ { "gen": { "height": 1072029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7da2f4cc9305d18302e7a092de318474ed6b8ea9f0c94e11c612e0216b4afc98" } } ], "extra": [ 1, 168, 73, 57, 27, 192, 60, 186, 101, 28, 138, 251, 240, 157, 232, 136, 111, 127, 179, 232, 117, 165, 108, 226, 141, 232, 90, 16, 101, 211, 173, 109, 196, 2, 17, 0, 0, 0, 6, 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