Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 471d9cf529f404aeab5dce5111037dcc7a7ddb5ebfd563e2f4ab5aa98f1aa920

Tx prefix hash: 475c5bade0b3b47bd550ad1cbc67fac390bde3fd4e6e4255d25a2ab63e9b9007
Tx public key: 33045ba92619ec21cd15a1b78401689172403c0f8218dc32fdcaeb24e73bad44
Timestamp: 1708259774 Timestamp [UCT]: 2024-02-18 12:36:14 Age [y:d:h:m:s]: 01:269:06:22:11
Block: 960225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 451192 RingCT/type: yes/0
Extra: 0133045ba92619ec21cd15a1b78401689172403c0f8218dc32fdcaeb24e73bad440211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f58c0f12d42fbb0bd2ad5567ae7b59eae99ed19047a3e08767804c528c004b0 0.600000000000 1419788 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": 960235, "vin": [ { "gen": { "height": 960225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f58c0f12d42fbb0bd2ad5567ae7b59eae99ed19047a3e08767804c528c004b0" } } ], "extra": [ 1, 51, 4, 91, 169, 38, 25, 236, 33, 205, 21, 161, 183, 132, 1, 104, 145, 114, 64, 60, 15, 130, 24, 220, 50, 253, 202, 235, 36, 231, 59, 173, 68, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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