Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec27910c9a6ebdf2b53dd79c94e6afd6235a490ef988d2cae5a35b3b21af387d

Tx prefix hash: 52a31829270bc07144caf1e338d868eddfb875b9c9075a95465e6b613b1e4cce
Tx public key: a51ff10de362d509755c570ca43a0c9f34bd4374bfe5e02a04ae39e9f6fae579
Timestamp: 1730791863 Timestamp [UCT]: 2024-11-05 07:31:03 Age [y:d:h:m:s]: 00:132:03:45:56
Block: 1146945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94292 RingCT/type: yes/0
Extra: 01a51ff10de362d509755c570ca43a0c9f34bd4374bfe5e02a04ae39e9f6fae579021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18348ca1bf3e048a5b1114218bcbf0cd807c9a6fc3504af69311277b70da5d51 0.600000000000 1631638 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": 1146955, "vin": [ { "gen": { "height": 1146945 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18348ca1bf3e048a5b1114218bcbf0cd807c9a6fc3504af69311277b70da5d51" } } ], "extra": [ 1, 165, 31, 241, 13, 227, 98, 213, 9, 117, 92, 87, 12, 164, 58, 12, 159, 52, 189, 67, 116, 191, 229, 224, 42, 4, 174, 57, 233, 246, 250, 229, 121, 2, 17, 0, 0, 0, 1, 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