Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2acb010f02140f1e7d9b11cf7d319e820eb85ffc50cdd09a1af9f37e4e72ec20

Tx prefix hash: 7627002c9c0756f143d529d29d4827bd1ed7d5c51c5d127dca333f892eb5025e
Tx public key: 414a3004e651dc0de813be016a9adc86d52e1c94cc7474392a3c991baae701ea
Timestamp: 1724221441 Timestamp [UCT]: 2024-08-21 06:24:01 Age [y:d:h:m:s]: 01:078:04:58:44
Block: 1092563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314335 RingCT/type: yes/0
Extra: 01414a3004e651dc0de813be016a9adc86d52e1c94cc7474392a3c991baae701ea021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cf5ffedf9deb55e6db1fe78fb35ee939d5b16ee94427964de2450fd21e494bc 0.600000000000 1567334 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": 1092573, "vin": [ { "gen": { "height": 1092563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cf5ffedf9deb55e6db1fe78fb35ee939d5b16ee94427964de2450fd21e494bc" } } ], "extra": [ 1, 65, 74, 48, 4, 230, 81, 220, 13, 232, 19, 190, 1, 106, 154, 220, 134, 213, 46, 28, 148, 204, 116, 116, 57, 42, 60, 153, 27, 170, 231, 1, 234, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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