Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f46dad75a5912d98d2ad41691b8fbd2bfefb0091bff9200e812a558f417d436d

Tx prefix hash: e2f6573c270c7a417c5b848b9d3f5db3525823be7747391d56102aa5b6d1d4c8
Tx public key: 741cb74b878fd6b8bf0766a13312cd825a61ec5b5fa4fe738153752cee84c2f5
Timestamp: 1736715826 Timestamp [UCT]: 2025-01-12 21:03:46 Age [y:d:h:m:s]: 00:064:03:05:00
Block: 1195992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45623 RingCT/type: yes/0
Extra: 01741cb74b878fd6b8bf0766a13312cd825a61ec5b5fa4fe738153752cee84c2f50211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57f28e7cb0a298d2d7ba1d57174c5113653e7930008e4f466158da58b0852370 0.600000000000 1682589 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": 1196002, "vin": [ { "gen": { "height": 1195992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57f28e7cb0a298d2d7ba1d57174c5113653e7930008e4f466158da58b0852370" } } ], "extra": [ 1, 116, 28, 183, 75, 135, 143, 214, 184, 191, 7, 102, 161, 51, 18, 205, 130, 90, 97, 236, 91, 95, 164, 254, 115, 129, 83, 117, 44, 238, 132, 194, 245, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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