Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58a6305f7cbb3023b71820a21aee69b78926bb6628e40546cf8992d31f8d7ef7

Tx prefix hash: 639b3a1ffdc056c394677c279dd30460c1d388c1b738ce6c921c9b077df52924
Tx public key: b6e1ec5d89181340a5fa9c3734d8342deae04b06b2286900b6fb22f26347fd90
Timestamp: 1751614663 Timestamp [UCT]: 2025-07-04 07:37:43 Age [y:d:h:m:s]: 00:139:06:52:26
Block: 1318475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97813 RingCT/type: yes/0
Extra: 01b6e1ec5d89181340a5fa9c3734d8342deae04b06b2286900b6fb22f26347fd9002110000000400f080dd000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4058d93dec8d7c6ae2970a75109b8311eb3fc4927ff14e6ee2a304f1d7e86b49 0.600000000000 1806156 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": 1318485, "vin": [ { "gen": { "height": 1318475 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4058d93dec8d7c6ae2970a75109b8311eb3fc4927ff14e6ee2a304f1d7e86b49" } } ], "extra": [ 1, 182, 225, 236, 93, 137, 24, 19, 64, 165, 250, 156, 55, 52, 216, 52, 45, 234, 224, 75, 6, 178, 40, 105, 0, 182, 251, 34, 242, 99, 71, 253, 144, 2, 17, 0, 0, 0, 4, 0, 240, 128, 221, 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