Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a89acf1acd8108d243e6ed2e863ee4b9d233b868713fcb30c5642153da09c46d

Tx prefix hash: 89bedf04708c4c397182b6179b89fe6570b0c5284cde02491e4b5801b864d00a
Tx public key: 98a5544c9254b4a5e5c03ac8a73df1ff20fced05cecdc7c52ded7c0ca5c4ddb4
Timestamp: 1722926085 Timestamp [UCT]: 2024-08-06 06:34:45 Age [y:d:h:m:s]: 01:153:23:09:11
Block: 1081804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368602 RingCT/type: yes/0
Extra: 0198a5544c9254b4a5e5c03ac8a73df1ff20fced05cecdc7c52ded7c0ca5c4ddb4021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec1404121160dbb256443ffc4ffab390fd88bf9e9f4ba544e4879ea7be605c09 0.600000000000 1555627 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": 1081814, "vin": [ { "gen": { "height": 1081804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec1404121160dbb256443ffc4ffab390fd88bf9e9f4ba544e4879ea7be605c09" } } ], "extra": [ 1, 152, 165, 84, 76, 146, 84, 180, 165, 229, 192, 58, 200, 167, 61, 241, 255, 32, 252, 237, 5, 206, 205, 199, 197, 45, 237, 124, 12, 165, 196, 221, 180, 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