Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3219f37c6046dc3f8e91b5581d12c64cb5efa3f8d99fcbeac316c08cd74a6c3

Tx prefix hash: cbabb5e744fb3d37194a027523f19cc1f2e11e5dbe3c882a03cf550969999b9a
Tx public key: f5aa7972e461f923d35998ffac66adc92b36a1e90e3923e67ed166cb16c024db
Timestamp: 1729838682 Timestamp [UCT]: 2024-10-25 06:44:42 Age [y:d:h:m:s]: 00:197:12:47:02
Block: 1139083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140996 RingCT/type: yes/0
Extra: 01f5aa7972e461f923d35998ffac66adc92b36a1e90e3923e67ed166cb16c024db0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 365bbe8caa6ba6895623307f892b0295f7d9a313570c2cf2378a70af9b491f75 0.600000000000 1622844 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": 1139093, "vin": [ { "gen": { "height": 1139083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "365bbe8caa6ba6895623307f892b0295f7d9a313570c2cf2378a70af9b491f75" } } ], "extra": [ 1, 245, 170, 121, 114, 228, 97, 249, 35, 211, 89, 152, 255, 172, 102, 173, 201, 43, 54, 161, 233, 14, 57, 35, 230, 126, 209, 102, 203, 22, 192, 36, 219, 2, 17, 0, 0, 0, 5, 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