Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a84f7aa1bfd97f2fe27850ec4ac7a06283fb8a6dc75e8067d80b65e2c3da28b9

Tx prefix hash: 4c2a0110836868efe067813d36ff586760567a65f12c2b1540899f0390f64c66
Tx public key: bed69a46cf32e81bc4347a7c10d2c0f048029026d1a4b23a858f191d2055d011
Timestamp: 1748646107 Timestamp [UCT]: 2025-05-30 23:01:47 Age [y:d:h:m:s]: 00:238:02:01:32
Block: 1294501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167756 RingCT/type: yes/0
Extra: 01bed69a46cf32e81bc4347a7c10d2c0f048029026d1a4b23a858f191d2055d011021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffa14f661840392a9d6f8ba64915ede316d6a85fb52e5070d30cf033d13a6c0d 0.600000000000 1781996 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": 1294511, "vin": [ { "gen": { "height": 1294501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffa14f661840392a9d6f8ba64915ede316d6a85fb52e5070d30cf033d13a6c0d" } } ], "extra": [ 1, 190, 214, 154, 70, 207, 50, 232, 27, 196, 52, 122, 124, 16, 210, 192, 240, 72, 2, 144, 38, 209, 164, 178, 58, 133, 143, 25, 29, 32, 85, 208, 17, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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