Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c58533fa6fc833c0258d940a3bedff22747e31401df1b114d32056afe209d6e

Tx prefix hash: 2c970641ffee439d6a32c20fe2c1f91de0e4e469ffb21396c1f0667daae9e86d
Tx public key: 4395d825dcb1b38c0b6112f8bad7631d4e3964fd7b8bf85e578ec49b28ba5919
Timestamp: 1741604146 Timestamp [UCT]: 2025-03-10 10:55:46 Age [y:d:h:m:s]: 00:255:08:02:34
Block: 1236213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180217 RingCT/type: yes/0
Extra: 014395d825dcb1b38c0b6112f8bad7631d4e3964fd7b8bf85e578ec49b28ba5919021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b973ec48e29b52d1323d9f81a2883d14ab957e1545ca6200b050f48e0901474a 0.600000000000 1723158 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": 1236223, "vin": [ { "gen": { "height": 1236213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b973ec48e29b52d1323d9f81a2883d14ab957e1545ca6200b050f48e0901474a" } } ], "extra": [ 1, 67, 149, 216, 37, 220, 177, 179, 140, 11, 97, 18, 248, 186, 215, 99, 29, 78, 57, 100, 253, 123, 139, 248, 94, 87, 142, 196, 155, 40, 186, 89, 25, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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