Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78f37164e63f306dd0b15d754db8b127d2df2938792fe1ffae24c7cbd63dcfac

Tx prefix hash: 8fb4bf58d8cdbcccd7c72a4485a6d41903f9956fabb7c0003a8b03e41b10e55c
Tx public key: 0f72fd32ba29eeaf3e33b44604744eb4b2e7949e62d64ea3cbf8f79cd9ca01f3
Timestamp: 1740331866 Timestamp [UCT]: 2025-02-23 17:31:06 Age [y:d:h:m:s]: 00:226:14:18:56
Block: 1225645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159660 RingCT/type: yes/0
Extra: 010f72fd32ba29eeaf3e33b44604744eb4b2e7949e62d64ea3cbf8f79cd9ca01f30211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2040c3ed89390bfa1c4b8f4ccd87cca00d1878469d68a9fa6316726820bd05ab 0.600000000000 1712512 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": 1225655, "vin": [ { "gen": { "height": 1225645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2040c3ed89390bfa1c4b8f4ccd87cca00d1878469d68a9fa6316726820bd05ab" } } ], "extra": [ 1, 15, 114, 253, 50, 186, 41, 238, 175, 62, 51, 180, 70, 4, 116, 78, 180, 178, 231, 148, 158, 98, 214, 78, 163, 203, 248, 247, 156, 217, 202, 1, 243, 2, 17, 0, 0, 0, 7, 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