Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 226099a22e5e00b546cf471583697cf67d6663a696c6d880f49148b5424cc7d4

Tx prefix hash: a330623539d36113708da932765b40dda411d967c9aa36b41138f87dcdb5e929
Tx public key: f80f4f2fb43b0e3b47b50a2fb5035b56428bfb8aa410f8544edd67e11e87d44c
Timestamp: 1705659637 Timestamp [UCT]: 2024-01-19 10:20:37 Age [y:d:h:m:s]: 00:299:23:23:29
Block: 938632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214810 RingCT/type: yes/0
Extra: 01f80f4f2fb43b0e3b47b50a2fb5035b56428bfb8aa410f8544edd67e11e87d44c0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c2cad677c2c64a08fee31f42d7546d1a743e1479227bfacb1db9af918de7006 0.600000000000 1396702 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": 938642, "vin": [ { "gen": { "height": 938632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c2cad677c2c64a08fee31f42d7546d1a743e1479227bfacb1db9af918de7006" } } ], "extra": [ 1, 248, 15, 79, 47, 180, 59, 14, 59, 71, 181, 10, 47, 181, 3, 91, 86, 66, 139, 251, 138, 164, 16, 248, 84, 78, 221, 103, 225, 30, 135, 212, 76, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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