Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92b06789159d885762024006089c0c3a32cb62cca9e1c22e377bcceb14a87a43

Tx prefix hash: 369ab1a9a44f0ece07a559edfb5b861fa7a63aafe7f1e68fef4f269c977fc14c
Tx public key: 0d038f5b3e799dc96c6e9d724fbf00f9ef60b03515f45dadb177027a2b580768
Timestamp: 1588735061 Timestamp [UCT]: 2020-05-06 03:17:41 Age [y:d:h:m:s]: 04:313:02:37:48
Block: 98797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1140122 RingCT/type: yes/0
Extra: 010d038f5b3e799dc96c6e9d724fbf00f9ef60b03515f45dadb177027a2b58076802110000000339be35fb000000000000000000

1 output(s) for total of 288.849938414000 dcy

stealth address amount amount idx
00: 04bd07f5d477c459d150210d8f97e91e8ff4c84250862c4884d97a9aa6c83eab 288.849938414000 174559 of 0

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": 98807, "vin": [ { "gen": { "height": 98797 } } ], "vout": [ { "amount": 288849938414, "target": { "key": "04bd07f5d477c459d150210d8f97e91e8ff4c84250862c4884d97a9aa6c83eab" } } ], "extra": [ 1, 13, 3, 143, 91, 62, 121, 157, 201, 108, 110, 157, 114, 79, 191, 0, 249, 239, 96, 176, 53, 21, 244, 93, 173, 177, 119, 2, 122, 43, 88, 7, 104, 2, 17, 0, 0, 0, 3, 57, 190, 53, 251, 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