Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ff040898fcdc4a2ee56e0748cfa08af5811c06a6062d4d287ca69785a41329e

Tx prefix hash: ea9aeb0add86a033bf683339dba5d53b449463cf0b4c1c8900bb1700a36fb87a
Tx public key: a733768a8717526e40893c82bee5a2d6c1bd61e0683c9f5a35de8d8b35381e1d
Timestamp: 1742506604 Timestamp [UCT]: 2025-03-20 21:36:44 Age [y:d:h:m:s]: 00:088:10:29:32
Block: 1243687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63128 RingCT/type: yes/0
Extra: 01a733768a8717526e40893c82bee5a2d6c1bd61e0683c9f5a35de8d8b35381e1d021100000005bfa77623000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8b4fbd958185316c34e56536fda9f6e04e55493d99ef79a8253c006f9473a7b 0.600000000000 1730674 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": 1243697, "vin": [ { "gen": { "height": 1243687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8b4fbd958185316c34e56536fda9f6e04e55493d99ef79a8253c006f9473a7b" } } ], "extra": [ 1, 167, 51, 118, 138, 135, 23, 82, 110, 64, 137, 60, 130, 190, 229, 162, 214, 193, 189, 97, 224, 104, 60, 159, 90, 53, 222, 141, 139, 53, 56, 30, 29, 2, 17, 0, 0, 0, 5, 191, 167, 118, 35, 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