Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab5048c63a89770e0c497ca33eed33a084851767caf4d330d7e6034b5dfd5d39

Tx prefix hash: a538e9dd03019b0f28b9764873e3db3c265e0997b5516df1d18b41203072bf2e
Tx public key: e2c66e7e3ee757e7211ce9e56713867e2eab97d5d983b31f0985efdaee872512
Timestamp: 1716368722 Timestamp [UCT]: 2024-05-22 09:05:22 Age [y:d:h:m:s]: 00:339:10:16:06
Block: 1027460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242615 RingCT/type: yes/0
Extra: 01e2c66e7e3ee757e7211ce9e56713867e2eab97d5d983b31f0985efdaee87251202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bdb1ceb4f239b7a938597133c5aa43891ec7c077a24b2da5e0fc5c6f86f97fd 0.600000000000 1495087 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": 1027470, "vin": [ { "gen": { "height": 1027460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bdb1ceb4f239b7a938597133c5aa43891ec7c077a24b2da5e0fc5c6f86f97fd" } } ], "extra": [ 1, 226, 198, 110, 126, 62, 231, 87, 231, 33, 28, 233, 229, 103, 19, 134, 126, 46, 171, 151, 213, 217, 131, 179, 31, 9, 133, 239, 218, 238, 135, 37, 18, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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