Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92db92261bfb768d7524057a8121dd191e88ef63744da807538e4d607914127a

Tx prefix hash: b4e865fd84fd97a921322c2f40aedfcc82a9d1b6169b86cbd3c6047c7a14c5df
Tx public key: 806b0ebeb13f6bab4eee065b305cac52ea333cb6889d48ee6e91e2f10700335b
Timestamp: 1722517412 Timestamp [UCT]: 2024-08-01 13:03:32 Age [y:d:h:m:s]: 00:300:15:52:52
Block: 1078427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214831 RingCT/type: yes/0
Extra: 01806b0ebeb13f6bab4eee065b305cac52ea333cb6889d48ee6e91e2f10700335b021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a52c8df5c7ae85a051d479f0a862bad011bfd1cc333c3cd43a35981221886d0 0.600000000000 1551004 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": 1078437, "vin": [ { "gen": { "height": 1078427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a52c8df5c7ae85a051d479f0a862bad011bfd1cc333c3cd43a35981221886d0" } } ], "extra": [ 1, 128, 107, 14, 190, 177, 63, 107, 171, 78, 238, 6, 91, 48, 92, 172, 82, 234, 51, 60, 182, 136, 157, 72, 238, 110, 145, 226, 241, 7, 0, 51, 91, 2, 17, 0, 0, 0, 6, 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