Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03fe7c3d7313c829554bd60b90a99e3f8591847b6ffcd814a0c2ceac0c440105

Tx prefix hash: e7ee468ccc584c94ee9a33dcb55b04ac2b4e273ea7da62664ac5b2a81ee88ef9
Tx public key: 496a3f7c1316f184774a1326e5e4be8e1a4b6eb2b535563f0dc22efc1df35d37
Timestamp: 1736251712 Timestamp [UCT]: 2025-01-07 12:08:32 Age [y:d:h:m:s]: 00:344:01:45:24
Block: 1192149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243460 RingCT/type: yes/0
Extra: 01496a3f7c1316f184774a1326e5e4be8e1a4b6eb2b535563f0dc22efc1df35d37021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23de27f0068e13db8ba3a19adbf019c10cfb600994e16d822dedd3c1a7c09763 0.600000000000 1678696 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": 1192159, "vin": [ { "gen": { "height": 1192149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23de27f0068e13db8ba3a19adbf019c10cfb600994e16d822dedd3c1a7c09763" } } ], "extra": [ 1, 73, 106, 63, 124, 19, 22, 241, 132, 119, 74, 19, 38, 229, 228, 190, 142, 26, 75, 110, 178, 181, 53, 86, 63, 13, 194, 46, 252, 29, 243, 93, 55, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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