Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01eaa460ee2871ab15afe33d31e848a1c88bfa2b7db9e89e747797d04d1fbcb5

Tx prefix hash: ed02168309dc71723e13711d6b22405b6c59a6ef37715d555e04ad7cd321c128
Tx public key: c9a0e011e5b94f7e6fbe3df970fe9b4b15e52d50414c46f5ac3aeac2d3a783ac
Timestamp: 1732059280 Timestamp [UCT]: 2024-11-19 23:34:40 Age [y:d:h:m:s]: 00:004:07:13:29
Block: 1157444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3072 RingCT/type: yes/0
Extra: 01c9a0e011e5b94f7e6fbe3df970fe9b4b15e52d50414c46f5ac3aeac2d3a783ac021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d2aea8e32a483f3479b5c6254a24ecfff953c93f8d461b83bda471b549d0632 0.600000000000 1643067 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": 1157454, "vin": [ { "gen": { "height": 1157444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d2aea8e32a483f3479b5c6254a24ecfff953c93f8d461b83bda471b549d0632" } } ], "extra": [ 1, 201, 160, 224, 17, 229, 185, 79, 126, 111, 190, 61, 249, 112, 254, 155, 75, 21, 229, 45, 80, 65, 76, 70, 245, 172, 58, 234, 194, 211, 167, 131, 172, 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