Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0553128e2b5a4fbdefc6d22caeee371865aaae316e2a93d7669314e58caacd6

Tx prefix hash: 6120473047c773aa33e4350fd791cd6a84ad7f11f6849adfef34abff614e0a89
Tx public key: 830e4c973b392be99815babc5c59dd7821c6c45007b0ba1bc4ef66e8b862e67c
Timestamp: 1738052291 Timestamp [UCT]: 2025-01-28 08:18:11 Age [y:d:h:m:s]: 00:329:11:29:36
Block: 1206813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233261 RingCT/type: yes/0
Extra: 01830e4c973b392be99815babc5c59dd7821c6c45007b0ba1bc4ef66e8b862e67c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a0b3ad4df45627cb7a0177b26bd1fc90ad5885c93c0d037b2b1ac999ca188cc 0.600000000000 1693526 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": 1206823, "vin": [ { "gen": { "height": 1206813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a0b3ad4df45627cb7a0177b26bd1fc90ad5885c93c0d037b2b1ac999ca188cc" } } ], "extra": [ 1, 131, 14, 76, 151, 59, 57, 43, 233, 152, 21, 186, 188, 92, 89, 221, 120, 33, 198, 196, 80, 7, 176, 186, 27, 196, 239, 102, 232, 184, 98, 230, 124, 2, 17, 0, 0, 0, 3, 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