Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1fe0b5216003a5d062ee8099663ba3dd3bd3fb3927e522798109852e27c69ac

Tx prefix hash: 7442f48ff02c40b034706d291edd0aa24a73b1e96223c792bfff60528cc6fb7e
Tx public key: 99c43152120a07001de7f4fb35a5fc8496eba6eb7d760d20ec0c0e566a727abe
Timestamp: 1577738701 Timestamp [UCT]: 2019-12-30 20:45:01 Age [y:d:h:m:s]: 05:002:00:43:23
Block: 35316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151390 RingCT/type: yes/0
Extra: 0199c43152120a07001de7f4fb35a5fc8496eba6eb7d760d20ec0c0e566a727abe021100000005d81c26c0000000000000000000

1 output(s) for total of 468.796419598000 dcy

stealth address amount amount idx
00: e9abf9d384ab7c27350aae6e8884808a88ad3a9726514c262e61dc2dc7408c04 468.796419598000 59488 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": 35326, "vin": [ { "gen": { "height": 35316 } } ], "vout": [ { "amount": 468796419598, "target": { "key": "e9abf9d384ab7c27350aae6e8884808a88ad3a9726514c262e61dc2dc7408c04" } } ], "extra": [ 1, 153, 196, 49, 82, 18, 10, 7, 0, 29, 231, 244, 251, 53, 165, 252, 132, 150, 235, 166, 235, 125, 118, 13, 32, 236, 12, 14, 86, 106, 114, 122, 190, 2, 17, 0, 0, 0, 5, 216, 28, 38, 192, 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