Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ebc8948f47336fcf96a80d618acdf29b5bc2d6577d8db2301d5011d33db3fe1

Tx prefix hash: 3b3041e3c0507fed4d557e1407475abaa1f306fb7137eee942d6419846edffd2
Tx public key: ffab7ba1572e4b6789012b0086a7de01e8a3e939343ec52bc8d803a335ed8ca0
Timestamp: 1727594320 Timestamp [UCT]: 2024-09-29 07:18:40 Age [y:d:h:m:s]: 00:261:00:33:13
Block: 1120520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186287 RingCT/type: yes/0
Extra: 01ffab7ba1572e4b6789012b0086a7de01e8a3e939343ec52bc8d803a335ed8ca0021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92a6e4d902b77aaf8cc02106d5606dcf0d08a56e837afe4657ff4592e1e758fc 0.600000000000 1602463 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": 1120530, "vin": [ { "gen": { "height": 1120520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92a6e4d902b77aaf8cc02106d5606dcf0d08a56e837afe4657ff4592e1e758fc" } } ], "extra": [ 1, 255, 171, 123, 161, 87, 46, 75, 103, 137, 1, 43, 0, 134, 167, 222, 1, 232, 163, 233, 57, 52, 62, 197, 43, 200, 216, 3, 163, 53, 237, 140, 160, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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