Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc3ec7dfab1cc730c8e12d9328cee9dcabbb3539d99984e81bed2b0630dfcdca

Tx prefix hash: 9d2ea3637c0cdfff607b0381e591d4f1e1c8b2c8a11ec8ae38acae4986ec5808
Tx public key: 0d93ffeb061271477144d91563d4d34a167a85c24f52945ddacb56b53747455e
Timestamp: 1705416220 Timestamp [UCT]: 2024-01-16 14:43:40 Age [y:d:h:m:s]: 01:294:14:23:02
Block: 936632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469351 RingCT/type: yes/0
Extra: 010d93ffeb061271477144d91563d4d34a167a85c24f52945ddacb56b53747455e02110000000252d47e94000000000000000000

1 output(s) for total of 0.600040000000 dcy

stealth address amount amount idx
00: d3948cd4e53801fc02f12155a8e11c1fe3bb9c971546d2f58be1e9678a5bf2cb 0.600040000000 1394666 of 0

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": 936642, "vin": [ { "gen": { "height": 936632 } } ], "vout": [ { "amount": 600040000, "target": { "key": "d3948cd4e53801fc02f12155a8e11c1fe3bb9c971546d2f58be1e9678a5bf2cb" } } ], "extra": [ 1, 13, 147, 255, 235, 6, 18, 113, 71, 113, 68, 217, 21, 99, 212, 211, 74, 22, 122, 133, 194, 79, 82, 148, 93, 218, 203, 86, 181, 55, 71, 69, 94, 2, 17, 0, 0, 0, 2, 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