Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83091e4d050632f632a81278b98c9929166c20cf957cde8ccf2d6d0ff71cd2bb

Tx prefix hash: 1cc72cf4e3dc8317ac20f59c092717ab215bc2cea03202ca359f36c2efeb8061
Tx public key: ba72f9d26e86e8f3d494fcf408d15ab19b9b98d88d2e2f3840dc5678f4267173
Timestamp: 1726476358 Timestamp [UCT]: 2024-09-16 08:45:58 Age [y:d:h:m:s]: 01:056:16:21:34
Block: 1111257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298918 RingCT/type: yes/0
Extra: 01ba72f9d26e86e8f3d494fcf408d15ab19b9b98d88d2e2f3840dc5678f4267173021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98e44a7b211c72ccb4cdfe15b7a34c28e75d6bbfad8a40a5cf88dd80c69e3108 0.600000000000 1590148 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": 1111267, "vin": [ { "gen": { "height": 1111257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98e44a7b211c72ccb4cdfe15b7a34c28e75d6bbfad8a40a5cf88dd80c69e3108" } } ], "extra": [ 1, 186, 114, 249, 210, 110, 134, 232, 243, 212, 148, 252, 244, 8, 209, 90, 177, 155, 155, 152, 216, 141, 46, 47, 56, 64, 220, 86, 120, 244, 38, 113, 115, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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