Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e80162c7de1b5d10827650c672ec1903a861357efe4dd6a64e252f71041d57e9

Tx prefix hash: b5cbf63b1bdad2443b69e0dbeede10c79c31336057351dcd328ed2a42e3dcd45
Tx public key: ad2a634f33bace92b497e84e82163b5cf1ef5b17d8fe0a1baeb40f1c679ed36d
Timestamp: 1737644349 Timestamp [UCT]: 2025-01-23 14:59:09 Age [y:d:h:m:s]: 00:301:07:30:26
Block: 1203644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212888 RingCT/type: yes/0
Extra: 01ad2a634f33bace92b497e84e82163b5cf1ef5b17d8fe0a1baeb40f1c679ed36d02110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bb7753e88f4f03412bd7da4f7990d6bd5a99182b1c959616e8001690e3f3999 0.600000000000 1690323 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": 1203654, "vin": [ { "gen": { "height": 1203644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bb7753e88f4f03412bd7da4f7990d6bd5a99182b1c959616e8001690e3f3999" } } ], "extra": [ 1, 173, 42, 99, 79, 51, 186, 206, 146, 180, 151, 232, 78, 130, 22, 59, 92, 241, 239, 91, 23, 216, 254, 10, 27, 174, 180, 15, 28, 103, 158, 211, 109, 2, 17, 0, 0, 0, 12, 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