Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b4107b868fcb45a9e9dd8a665598178246bc4721a17ab1b810e08a548883800

Tx prefix hash: a7a4eca12c492fc7930d46f84e7c0030f975ef43dc5fdf8b9b2fb5de0af0be3c
Tx public key: 192de344006987fd8964cd62100e0d32f0a6b407793879fa0924aa14df4c1b70
Timestamp: 1701669210 Timestamp [UCT]: 2023-12-04 05:53:30 Age [y:d:h:m:s]: 01:177:23:16:50
Block: 905573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388400 RingCT/type: yes/0
Extra: 01192de344006987fd8964cd62100e0d32f0a6b407793879fa0924aa14df4c1b7002110000000375e3f0e9000000000000000000

1 output(s) for total of 0.613000325000 dcy

stealth address amount amount idx
00: 6fa38949bb8004958c1f46e3d6f65c8500a36d47393321b8bba2585f607144b2 0.613000325000 1362462 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": 905583, "vin": [ { "gen": { "height": 905573 } } ], "vout": [ { "amount": 613000325, "target": { "key": "6fa38949bb8004958c1f46e3d6f65c8500a36d47393321b8bba2585f607144b2" } } ], "extra": [ 1, 25, 45, 227, 68, 0, 105, 135, 253, 137, 100, 205, 98, 16, 14, 13, 50, 240, 166, 180, 7, 121, 56, 121, 250, 9, 36, 170, 20, 223, 76, 27, 112, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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