Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edead0346039a86eea30ef6272103e9cb1a3dbb5b9f7e60407fa0bcfb854e441

Tx prefix hash: acadc8a860cab0f53bdb695158a73590d42ad054186a8dafc6ea8b732473842b
Tx public key: 4576cfb47aa9aa0c733342f92f137d4f8b672e0b401e8d9934df10fe8fbfcd40
Timestamp: 1723749318 Timestamp [UCT]: 2024-08-15 19:15:18 Age [y:d:h:m:s]: 00:191:03:16:26
Block: 1088639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136440 RingCT/type: yes/0
Extra: 014576cfb47aa9aa0c733342f92f137d4f8b672e0b401e8d9934df10fe8fbfcd4002110000001de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f46fa31d1b4d529307662c386e6ab2497e6104bf780cc03ca86d1e13770534c0 0.600000000000 1563256 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": 1088649, "vin": [ { "gen": { "height": 1088639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f46fa31d1b4d529307662c386e6ab2497e6104bf780cc03ca86d1e13770534c0" } } ], "extra": [ 1, 69, 118, 207, 180, 122, 169, 170, 12, 115, 51, 66, 249, 47, 19, 125, 79, 139, 103, 46, 11, 64, 30, 141, 153, 52, 223, 16, 254, 143, 191, 205, 64, 2, 17, 0, 0, 0, 29, 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