Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4b4db77b0cc44595f557cc79e22ee851b47f9dddc4bd594fd91189d4749960e

Tx prefix hash: 50f42e167080fbcccb029203a69f86aa27716456964b6f2da010f5d2ac133b2b
Tx public key: c219f9746bfd0cbda73e6acd53d5f7974913fab1f747a2e93f4988968685fc29
Timestamp: 1713972553 Timestamp [UCT]: 2024-04-24 15:29:13 Age [y:d:h:m:s]: 00:255:10:47:10
Block: 1007581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182860 RingCT/type: yes/0
Extra: 01c219f9746bfd0cbda73e6acd53d5f7974913fab1f747a2e93f4988968685fc290211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5055e1bb7c9e70fd516fd037a7e983ca772103021ea6085515aec8a945397a79 0.600000000000 1468973 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": 1007591, "vin": [ { "gen": { "height": 1007581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5055e1bb7c9e70fd516fd037a7e983ca772103021ea6085515aec8a945397a79" } } ], "extra": [ 1, 194, 25, 249, 116, 107, 253, 12, 189, 167, 62, 106, 205, 83, 213, 247, 151, 73, 19, 250, 177, 247, 71, 162, 233, 63, 73, 136, 150, 134, 133, 252, 41, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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