Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de540af71e398b01418b281d0b51f217548f5c68cca86676bd8f42acbafaedfc

Tx prefix hash: 9887bfebff92e5e046a2748d5817da748088016b9b698825f42257e534852e41
Tx public key: 1450bb7bd8824e62c2d0dfe6d9042d827cc76fe83bd9809e4f1a4e6076e1b409
Timestamp: 1734798641 Timestamp [UCT]: 2024-12-21 16:30:41 Age [y:d:h:m:s]: 00:101:09:01:13
Block: 1180156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72196 RingCT/type: yes/0
Extra: 011450bb7bd8824e62c2d0dfe6d9042d827cc76fe83bd9809e4f1a4e6076e1b409021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 019b728641dbbf68bcd2e1b3e17140ec526f6fc684f43e010163df511263f0a9 0.600000000000 1666561 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": 1180166, "vin": [ { "gen": { "height": 1180156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "019b728641dbbf68bcd2e1b3e17140ec526f6fc684f43e010163df511263f0a9" } } ], "extra": [ 1, 20, 80, 187, 123, 216, 130, 78, 98, 194, 208, 223, 230, 217, 4, 45, 130, 124, 199, 111, 232, 59, 217, 128, 158, 79, 26, 78, 96, 118, 225, 180, 9, 2, 17, 0, 0, 0, 7, 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