Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06b5f4f229eaefeae87ff5a60ed63b7bc00ccdb7b114cb9a8bfe96add03c5357

Tx prefix hash: e5de980e4e14454be3cb4cb1ed12c68dc92cb8e4afa2ce4423f4146fc1e3b189
Tx public key: fe9dc26cf371f1602984b5aca59e89a4d6d45df8420a88d1717c03268289d730
Timestamp: 1698359814 Timestamp [UCT]: 2023-10-26 22:36:54 Age [y:d:h:m:s]: 02:013:09:20:46
Block: 878369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 529146 RingCT/type: yes/0
Extra: 01fe9dc26cf371f1602984b5aca59e89a4d6d45df8420a88d1717c03268289d730021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.754395154000 dcy

stealth address amount amount idx
00: 6c39ba1fc779731ecf6083c4729ab6b563f5e9b96b9a1c0f7e9b8b3fac1bf168 0.754395154000 1333807 of 0

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": 878379, "vin": [ { "gen": { "height": 878369 } } ], "vout": [ { "amount": 754395154, "target": { "key": "6c39ba1fc779731ecf6083c4729ab6b563f5e9b96b9a1c0f7e9b8b3fac1bf168" } } ], "extra": [ 1, 254, 157, 194, 108, 243, 113, 241, 96, 41, 132, 181, 172, 165, 158, 137, 164, 214, 212, 93, 248, 66, 10, 136, 209, 113, 124, 3, 38, 130, 137, 215, 48, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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