Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edc62cf92001f748cbad61c50c9c361bd0e82fd74fc06bb9b84d82182a82b402

Tx prefix hash: 577dd07051a52dfd5b55f27832ecc005bb7f6cc105109f14956cc8e02a7355c9
Tx public key: 6fb230a0d23796f7b1acba6d1b9e0007c0aa7d9efb2e1fa19f4c20a8c7f9bcb0
Timestamp: 1742071053 Timestamp [UCT]: 2025-03-15 20:37:33 Age [y:d:h:m:s]: 00:298:21:28:09
Block: 1240079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211422 RingCT/type: yes/0
Extra: 016fb230a0d23796f7b1acba6d1b9e0007c0aa7d9efb2e1fa19f4c20a8c7f9bcb00211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e81334a43c52d78b7ebaf1a16fb9b0ccfa6c57ee10f76c84e51709de176fba87 0.600000000000 1727044 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": 1240089, "vin": [ { "gen": { "height": 1240079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e81334a43c52d78b7ebaf1a16fb9b0ccfa6c57ee10f76c84e51709de176fba87" } } ], "extra": [ 1, 111, 178, 48, 160, 210, 55, 150, 247, 177, 172, 186, 109, 27, 158, 0, 7, 192, 170, 125, 158, 251, 46, 31, 161, 159, 76, 32, 168, 199, 249, 188, 176, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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