Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b53a13e303dec48356f84d42f61f4b6905e01b846e3c562faaeec74dca653e4

Tx prefix hash: e17f2f8ad5ef8e760f539f30847565d2b8694ef764af06934386b7cf11896359
Tx public key: 841ca5bd6fa84254e40ddcc1530584c3c58c6ea6aa8e31cb168bcd650f1e7333
Timestamp: 1705607171 Timestamp [UCT]: 2024-01-18 19:46:11 Age [y:d:h:m:s]: 01:299:10:38:55
Block: 938216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472830 RingCT/type: yes/0
Extra: 01841ca5bd6fa84254e40ddcc1530584c3c58c6ea6aa8e31cb168bcd650f1e733302110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e207379d07791081377dbd7a1a2b8862d8295a615c14adfc9d5c50f3f6cef61e 0.600000000000 1396286 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": 938226, "vin": [ { "gen": { "height": 938216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e207379d07791081377dbd7a1a2b8862d8295a615c14adfc9d5c50f3f6cef61e" } } ], "extra": [ 1, 132, 28, 165, 189, 111, 168, 66, 84, 228, 13, 220, 193, 83, 5, 132, 195, 197, 140, 110, 166, 170, 142, 49, 203, 22, 139, 205, 101, 15, 30, 115, 51, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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