Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6401c488030d0ceca330447fc921b2df4b924033f96e4e611940b1d72bedeb27

Tx prefix hash: 03b82e6c278cef992dcbe1e988b0349b6fc9ef49f46b02289cd676af79768db8
Tx public key: 7187ef8af50b3662f5e16f2c5d973cd1427670adb5e7891f531b2597c0a469fd
Timestamp: 1747672040 Timestamp [UCT]: 2025-05-19 16:27:20 Age [y:d:h:m:s]: 00:141:09:02:57
Block: 1286436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98681 RingCT/type: yes/0
Extra: 017187ef8af50b3662f5e16f2c5d973cd1427670adb5e7891f531b2597c0a469fd0211000000101f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e073c0c7a0d1f053ce3f7005d2e6d8c44e90a2a973b004f8cd8b4c26365a97ef 0.600000000000 1773901 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": 1286446, "vin": [ { "gen": { "height": 1286436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e073c0c7a0d1f053ce3f7005d2e6d8c44e90a2a973b004f8cd8b4c26365a97ef" } } ], "extra": [ 1, 113, 135, 239, 138, 245, 11, 54, 98, 245, 225, 111, 44, 93, 151, 60, 209, 66, 118, 112, 173, 181, 231, 137, 31, 83, 27, 37, 151, 192, 164, 105, 253, 2, 17, 0, 0, 0, 16, 31, 144, 81, 122, 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