Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 407d96ef2cdc68234cc41498e25133c6724ee631f30dbcde8d16353ae071d983

Tx prefix hash: 98723fb1ccf2c6da20c4e6506b9292711b821dc5f894da9455b0fd3edcea60e9
Tx public key: 605d345e478958d0205e6d2cdb486de251e0abd7a406636f840d31cf240a5ccd
Timestamp: 1749718222 Timestamp [UCT]: 2025-06-12 08:50:22 Age [y:d:h:m:s]: 00:161:19:36:33
Block: 1303338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113362 RingCT/type: yes/0
Extra: 01605d345e478958d0205e6d2cdb486de251e0abd7a406636f840d31cf240a5ccd021100000006bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a073c7cb608951664044c2f9d71e21bbd896a26eff3feffc27320f2f5db53c9 0.600000000000 1790917 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": 1303348, "vin": [ { "gen": { "height": 1303338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a073c7cb608951664044c2f9d71e21bbd896a26eff3feffc27320f2f5db53c9" } } ], "extra": [ 1, 96, 93, 52, 94, 71, 137, 88, 208, 32, 94, 109, 44, 219, 72, 109, 226, 81, 224, 171, 215, 164, 6, 99, 111, 132, 13, 49, 207, 36, 10, 92, 205, 2, 17, 0, 0, 0, 6, 191, 81, 178, 162, 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