Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a3cc05c6c6e0c1a4186b104ce00de61bc1874d96607858e853dbc2ea9833b65

Tx prefix hash: 79f4eb6c17baaee2b8a28ca92ac94893d67f339e3d8f749faa6f6a0c4dcf6744
Tx public key: b6c2cb5b105d540b3ca95427cc1a859c68e87397a7d77d3599fe2de0dca1d274
Timestamp: 1727947438 Timestamp [UCT]: 2024-10-03 09:23:58 Age [y:d:h:m:s]: 00:259:16:08:05
Block: 1123444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185291 RingCT/type: yes/0
Extra: 01b6c2cb5b105d540b3ca95427cc1a859c68e87397a7d77d3599fe2de0dca1d27402110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db5fc71cac7ffd41bf861b4b2f1627c051de0ce65d9128dfa61d6b82eb97c042 0.600000000000 1605979 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": 1123454, "vin": [ { "gen": { "height": 1123444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db5fc71cac7ffd41bf861b4b2f1627c051de0ce65d9128dfa61d6b82eb97c042" } } ], "extra": [ 1, 182, 194, 203, 91, 16, 93, 84, 11, 60, 169, 84, 39, 204, 26, 133, 156, 104, 232, 115, 151, 167, 215, 125, 53, 153, 254, 45, 224, 220, 161, 210, 116, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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