Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a5803f41a5bb8315e861310fd0e521b480d36e94d912585789b7bbd2248d2e8

Tx prefix hash: f1cb4c760b9399c11dfee2ac5828ec753db942e238b7d564bdd9dcb4ab55098e
Tx public key: 93a092ee061429e778a5062e6bfdbabf39976c30ddfc63e7d65a2bad51a6f8ec
Timestamp: 1736355113 Timestamp [UCT]: 2025-01-08 16:51:53 Age [y:d:h:m:s]: 00:316:11:08:47
Block: 1193008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223682 RingCT/type: yes/0
Extra: 0193a092ee061429e778a5062e6bfdbabf39976c30ddfc63e7d65a2bad51a6f8ec021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 491320c9dc90a0f652977d15311ba50a14fd8d8a805a027d02c10e43a9f80e82 0.600000000000 1679565 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": 1193018, "vin": [ { "gen": { "height": 1193008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "491320c9dc90a0f652977d15311ba50a14fd8d8a805a027d02c10e43a9f80e82" } } ], "extra": [ 1, 147, 160, 146, 238, 6, 20, 41, 231, 120, 165, 6, 46, 107, 253, 186, 191, 57, 151, 108, 48, 221, 252, 99, 231, 214, 90, 43, 173, 81, 166, 248, 236, 2, 17, 0, 0, 0, 8, 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