Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca86e4029d5ba1210710bee9eaf433d801a1b4d8635047d5ea2dd4a922361f8f

Tx prefix hash: 364932e79e794b77e98826c494120c862a0ce4dc93c67aa9801d0d0dead8bd11
Tx public key: 3268e2478bfb1ee4adc9791f00a9d3c49cd6d13335e243a59cd2e33f69fb280a
Timestamp: 1743981292 Timestamp [UCT]: 2025-04-06 23:14:52 Age [y:d:h:m:s]: 00:031:05:03:08
Block: 1255859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22337 RingCT/type: yes/0
Extra: 013268e2478bfb1ee4adc9791f00a9d3c49cd6d13335e243a59cd2e33f69fb280a021100000003dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 161418c639dd4b248efb465890b7b4269c9e975df72d15b5a5dd8c12190da8ad 0.600000000000 1742966 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": 1255869, "vin": [ { "gen": { "height": 1255859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "161418c639dd4b248efb465890b7b4269c9e975df72d15b5a5dd8c12190da8ad" } } ], "extra": [ 1, 50, 104, 226, 71, 139, 251, 30, 228, 173, 201, 121, 31, 0, 169, 211, 196, 156, 214, 209, 51, 53, 226, 67, 165, 156, 210, 227, 63, 105, 251, 40, 10, 2, 17, 0, 0, 0, 3, 219, 181, 113, 193, 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