Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85f28cea1923893cffb025a1ef272f80484a41db6c3af40f7eff8892db8a5914

Tx prefix hash: 3544293ae44e81f84c6b2b4b49e8701b48b187d381cad33f8bb056116320c3b1
Tx public key: bc0b1b25846d1327de3b079c269afbd36a3eae387bbbcb602ba0884f1195468a
Timestamp: 1736398859 Timestamp [UCT]: 2025-01-09 05:00:59 Age [y:d:h:m:s]: 00:079:05:30:33
Block: 1193369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56409 RingCT/type: yes/0
Extra: 01bc0b1b25846d1327de3b079c269afbd36a3eae387bbbcb602ba0884f1195468a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9213e38cb9c33daa2d35f73ab3f6f1747578b9126625be9b29a036b814fd5cde 0.600000000000 1679928 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": 1193379, "vin": [ { "gen": { "height": 1193369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9213e38cb9c33daa2d35f73ab3f6f1747578b9126625be9b29a036b814fd5cde" } } ], "extra": [ 1, 188, 11, 27, 37, 132, 109, 19, 39, 222, 59, 7, 156, 38, 154, 251, 211, 106, 62, 174, 56, 123, 187, 203, 96, 43, 160, 136, 79, 17, 149, 70, 138, 2, 17, 0, 0, 0, 3, 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