Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df3a3a31294e40e8638dad681bd283c0782b19603e17873f75f12fba81c3e05d

Tx prefix hash: ba0ff82ded1cb30339a2945b84caa7487a768fe4f9431bd32bc8853c7d031bd0
Tx public key: 1a99e13b454d731003fd595e6936cf5327baaf6fa9a97a6dbb0d7f256ad5ad2f
Timestamp: 1716684742 Timestamp [UCT]: 2024-05-26 00:52:22 Age [y:d:h:m:s]: 01:136:00:22:16
Block: 1030073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355764 RingCT/type: yes/0
Extra: 011a99e13b454d731003fd595e6936cf5327baaf6fa9a97a6dbb0d7f256ad5ad2f02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c9997def3fdf5eea58d7e9f8d91ecf551b94989bffcaefd13befcef34f6fac5 0.600000000000 1498326 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": 1030083, "vin": [ { "gen": { "height": 1030073 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c9997def3fdf5eea58d7e9f8d91ecf551b94989bffcaefd13befcef34f6fac5" } } ], "extra": [ 1, 26, 153, 225, 59, 69, 77, 115, 16, 3, 253, 89, 94, 105, 54, 207, 83, 39, 186, 175, 111, 169, 169, 122, 109, 187, 13, 127, 37, 106, 213, 173, 47, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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