Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df144104e18ebaa4dbfcc1a8a36ff5d7a45fec72836c0a8babe7e8fc122d8d7b

Tx prefix hash: b81fed4ad9fcc6dd4f10a72a6fc272fbe2919bbf68964648df5052eb7a61ccbf
Tx public key: 212d6d6f4cf35f9037264e66bfb740a13c79e8f4d47b4d56275705b2e76fc11a
Timestamp: 1745532007 Timestamp [UCT]: 2025-04-24 22:00:07 Age [y:d:h:m:s]: 00:210:03:39:11
Block: 1268717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147901 RingCT/type: yes/0
Extra: 01212d6d6f4cf35f9037264e66bfb740a13c79e8f4d47b4d56275705b2e76fc11a0211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4ef4bbb127ac36b17b08182be8546efed851da1e0e6969459c1a712ecc13adc 0.600000000000 1755948 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": 1268727, "vin": [ { "gen": { "height": 1268717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4ef4bbb127ac36b17b08182be8546efed851da1e0e6969459c1a712ecc13adc" } } ], "extra": [ 1, 33, 45, 109, 111, 76, 243, 95, 144, 55, 38, 78, 102, 191, 183, 64, 161, 60, 121, 232, 244, 212, 123, 77, 86, 39, 87, 5, 178, 231, 111, 193, 26, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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