Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49e96324bc4634c73186494ca99035ebfaabaf3bba47b04850c45e91bd972c44

Tx prefix hash: 576c48c99de6a3373ae47f6305d559a2aaa22c5d7e22ae091e568c276cb83998
Tx public key: 53d30e5f5612b602b17a2bfd45e53d2e2940fcf6712ea4cff4ffeaf605d5c0ff
Timestamp: 1721722263 Timestamp [UCT]: 2024-07-23 08:11:03 Age [y:d:h:m:s]: 00:262:00:25:31
Block: 1071823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187196 RingCT/type: yes/0
Extra: 0153d30e5f5612b602b17a2bfd45e53d2e2940fcf6712ea4cff4ffeaf605d5c0ff021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a3d998326e270e4ac6b7adb20b177145b394f2f9716031ef4919f0b528c6461 0.600000000000 1544194 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": 1071833, "vin": [ { "gen": { "height": 1071823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a3d998326e270e4ac6b7adb20b177145b394f2f9716031ef4919f0b528c6461" } } ], "extra": [ 1, 83, 211, 14, 95, 86, 18, 182, 2, 177, 122, 43, 253, 69, 229, 61, 46, 41, 64, 252, 246, 113, 46, 164, 207, 244, 255, 234, 246, 5, 213, 192, 255, 2, 17, 0, 0, 0, 4, 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