Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75ac455fe5d54b67e0c5f353d3c359e98602c943e599dc21c337771e2564a236

Tx prefix hash: ec789dece3a2a98dec0add08548ed7185e639d13b094a1cb30b367710e130030
Tx public key: 9c9c519d2f912eb190bce4ea428421d37a7e37c68a236283992f69429c75296d
Timestamp: 1706602721 Timestamp [UCT]: 2024-01-30 08:18:41 Age [y:d:h:m:s]: 01:025:08:22:25
Block: 946469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279153 RingCT/type: yes/0
Extra: 019c9c519d2f912eb190bce4ea428421d37a7e37c68a236283992f69429c75296d0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69f8d911a549e3741d34fb6177bee5bbcd40c284099ef0927ae6d89e26490b9c 0.600000000000 1404801 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": 946479, "vin": [ { "gen": { "height": 946469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69f8d911a549e3741d34fb6177bee5bbcd40c284099ef0927ae6d89e26490b9c" } } ], "extra": [ 1, 156, 156, 81, 157, 47, 145, 46, 177, 144, 188, 228, 234, 66, 132, 33, 211, 122, 126, 55, 198, 138, 35, 98, 131, 153, 47, 105, 66, 156, 117, 41, 109, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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