Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3204c31f511f8fd6d6abaf3d2966ffb761a446570624b1456fbbd5e106ed56ff

Tx prefix hash: 6244a72cd813ca756774fdb4b191021e4e1fd9df5eaefb3fbf4887d01dbe8757
Tx public key: cdf9a8ab0b32e8c085f88031668c33c3670e6748a470dfca07baefbe33733093
Timestamp: 1708009043 Timestamp [UCT]: 2024-02-15 14:57:23 Age [y:d:h:m:s]: 01:043:07:40:31
Block: 958138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292002 RingCT/type: yes/0
Extra: 01cdf9a8ab0b32e8c085f88031668c33c3670e6748a470dfca07baefbe337330930211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b933e7b1bd6f8087aa42c08a0c7324e19dbbfbcc132d074cdbe67ece80c317a1 0.600000000000 1417491 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": 958148, "vin": [ { "gen": { "height": 958138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b933e7b1bd6f8087aa42c08a0c7324e19dbbfbcc132d074cdbe67ece80c317a1" } } ], "extra": [ 1, 205, 249, 168, 171, 11, 50, 232, 192, 133, 248, 128, 49, 102, 140, 51, 195, 103, 14, 103, 72, 164, 112, 223, 202, 7, 186, 239, 190, 51, 115, 48, 147, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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