Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a47f8cbad53a3dfc0e849c0cbf2c60bf229f75bab9070bda57015b60860fd01

Tx prefix hash: 112cf1db518fba51a58f2d5123a3bbf991df0df3fc6f02644dad4bc7b2c4d4bd
Tx public key: 35cdb37a6063a90456c2dc2621d9974f9f6c1135f3db1909cfbb4244aaef17fa
Timestamp: 1707173339 Timestamp [UCT]: 2024-02-05 22:48:59 Age [y:d:h:m:s]: 01:023:10:07:53
Block: 951201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277765 RingCT/type: yes/0
Extra: 0135cdb37a6063a90456c2dc2621d9974f9f6c1135f3db1909cfbb4244aaef17fa02110000000110a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19108813b400e4a8f8416fc6c856028d71be0726897139e9bda23a0d79303e93 0.600000000000 1409937 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": 951211, "vin": [ { "gen": { "height": 951201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19108813b400e4a8f8416fc6c856028d71be0726897139e9bda23a0d79303e93" } } ], "extra": [ 1, 53, 205, 179, 122, 96, 99, 169, 4, 86, 194, 220, 38, 33, 217, 151, 79, 159, 108, 17, 53, 243, 219, 25, 9, 207, 187, 66, 68, 170, 239, 23, 250, 2, 17, 0, 0, 0, 1, 16, 161, 116, 143, 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