Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8c7a9abdeb0fadaf89cfdb84bc5941e42f2bfa5076e8049f9a1f5eaf94f3139

Tx prefix hash: 4b5944b134086c0e2573261cad65385ee4501790a4b296dc4c24508c9fec3584
Tx public key: 49f5f8cf92a41e3a7ec7c9029f6ba5b048ac3128baa9f5963fd9b3532675605c
Timestamp: 1737868669 Timestamp [UCT]: 2025-01-26 05:17:49 Age [y:d:h:m:s]: 00:047:18:03:20
Block: 1205485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33959 RingCT/type: yes/0
Extra: 0149f5f8cf92a41e3a7ec7c9029f6ba5b048ac3128baa9f5963fd9b3532675605c021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43cea96970e29cacb8c6733222cb8476d4e90ce4b9f8351e5da2c053bab81827 0.600000000000 1692182 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": 1205495, "vin": [ { "gen": { "height": 1205485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43cea96970e29cacb8c6733222cb8476d4e90ce4b9f8351e5da2c053bab81827" } } ], "extra": [ 1, 73, 245, 248, 207, 146, 164, 30, 58, 126, 199, 201, 2, 159, 107, 165, 176, 72, 172, 49, 40, 186, 169, 245, 150, 63, 217, 179, 83, 38, 117, 96, 92, 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