Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a2ae39ee5bb266d24e8951e8a1cd7890b30d041717ac109921e2632301f0472

Tx prefix hash: ec7124862f1e3bf0a991a7407bd1176aed16b56a3f681287560a04b68520d060
Tx public key: 1a88510e7c723e2889b26ee84e51e877f4c7472bef2aaf1ac4b32b00f36ab720
Timestamp: 1705340631 Timestamp [UCT]: 2024-01-15 17:43:51 Age [y:d:h:m:s]: 01:151:17:34:56
Block: 936004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369495 RingCT/type: yes/0
Extra: 011a88510e7c723e2889b26ee84e51e877f4c7472bef2aaf1ac4b32b00f36ab72002110000000d0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3ca3122453bd64ecf6d4c42333a1c72869ad6a5d6e9875a034c6e362b54d1a2 0.600000000000 1394026 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": 936014, "vin": [ { "gen": { "height": 936004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3ca3122453bd64ecf6d4c42333a1c72869ad6a5d6e9875a034c6e362b54d1a2" } } ], "extra": [ 1, 26, 136, 81, 14, 124, 114, 62, 40, 137, 178, 110, 232, 78, 81, 232, 119, 244, 199, 71, 43, 239, 42, 175, 26, 196, 179, 43, 0, 243, 106, 183, 32, 2, 17, 0, 0, 0, 13, 0, 17, 5, 91, 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