Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a9ecd6a3de65d1220e458a871c6f037ee6edb4ca60e0f4f236a628a15459dae

Tx prefix hash: 0abfcbb4e53e1b3bd9fa160f8d7da85fcecfe798009fcea0f77e0c6d0d92db47
Tx public key: e11f096877c38766e82b21259048453e4efc7a451062916613f5775b6b1384d2
Timestamp: 1728285299 Timestamp [UCT]: 2024-10-07 07:14:59 Age [y:d:h:m:s]: 00:179:08:02:55
Block: 1126250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127961 RingCT/type: yes/0
Extra: 01e11f096877c38766e82b21259048453e4efc7a451062916613f5775b6b1384d202110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c70c56c489b760213ea40f76d024d8aa20d7ff703d65b890ded14dde0e9c593d 0.600000000000 1609039 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": 1126260, "vin": [ { "gen": { "height": 1126250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c70c56c489b760213ea40f76d024d8aa20d7ff703d65b890ded14dde0e9c593d" } } ], "extra": [ 1, 225, 31, 9, 104, 119, 195, 135, 102, 232, 43, 33, 37, 144, 72, 69, 62, 78, 252, 122, 69, 16, 98, 145, 102, 19, 245, 119, 91, 107, 19, 132, 210, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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