Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e894a1cf7834264f76ffc177f91d13d92ec1c521e38ebdb86d7f92bdca8c233

Tx prefix hash: 0892004e735581f3037080c2d4e8fee175181a7558a6a021fc4cbcb2b545f282
Tx public key: 0cbe04978be69485c2e1e98793381219a4c30905944534d57b2dc5423e55dc0d
Timestamp: 1731371299 Timestamp [UCT]: 2024-11-12 00:28:19 Age [y:d:h:m:s]: 00:153:09:03:05
Block: 1151727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109463 RingCT/type: yes/0
Extra: 010cbe04978be69485c2e1e98793381219a4c30905944534d57b2dc5423e55dc0d0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aaadadc6950c9735f807144f393924f9b9a6973a1b42081191f9838b9a130584 0.600000000000 1637308 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": 1151737, "vin": [ { "gen": { "height": 1151727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aaadadc6950c9735f807144f393924f9b9a6973a1b42081191f9838b9a130584" } } ], "extra": [ 1, 12, 190, 4, 151, 139, 230, 148, 133, 194, 225, 233, 135, 147, 56, 18, 25, 164, 195, 9, 5, 148, 69, 52, 213, 123, 45, 197, 66, 62, 85, 220, 13, 2, 17, 0, 0, 0, 1, 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