Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e50152d093ff59632c0aee5765cd0e42465efc17b8fdcc9a7e9ffb5dd464b1a9

Tx prefix hash: 301292050a017fb52b094e9c865b5eab33cc033e7de580d03b59b1cd7745cd94
Tx public key: 2ce57fcb175b1fe9ec614205b4fa7d55f240c3d2b490c4ec87d5687c4db63310
Timestamp: 1703814533 Timestamp [UCT]: 2023-12-29 01:48:53 Age [y:d:h:m:s]: 01:122:01:18:01
Block: 923364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348371 RingCT/type: yes/0
Extra: 012ce57fcb175b1fe9ec614205b4fa7d55f240c3d2b490c4ec87d5687c4db63310021100000004ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3aeede19eea8f9f48ff604ca2f567a3eaa7075cf9cc592acc18cc6f6d6e342c 0.600000000000 1381096 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": 923374, "vin": [ { "gen": { "height": 923364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3aeede19eea8f9f48ff604ca2f567a3eaa7075cf9cc592acc18cc6f6d6e342c" } } ], "extra": [ 1, 44, 229, 127, 203, 23, 91, 31, 233, 236, 97, 66, 5, 180, 250, 125, 85, 242, 64, 195, 210, 180, 144, 196, 236, 135, 213, 104, 124, 77, 182, 51, 16, 2, 17, 0, 0, 0, 4, 173, 86, 148, 172, 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