Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 805b48e96cfc6f13f5ed6c34f630cf6fd3f66076186278c86a4a7b7b43114c92

Tx prefix hash: 432280ddb3ea6768a5342bbf980f1079ec4cb69500eee3a8a6e7746bb68540e2
Tx public key: bf9308341516042bd8f2dd13d4ab93ffa5cf2c74d412bce05526e2bcab7f9de7
Timestamp: 1724428352 Timestamp [UCT]: 2024-08-23 15:52:32 Age [y:d:h:m:s]: 00:235:18:30:51
Block: 1094285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168361 RingCT/type: yes/0
Extra: 01bf9308341516042bd8f2dd13d4ab93ffa5cf2c74d412bce05526e2bcab7f9de7021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b114df0341f8b6a3e930a3a55592d898bcd8309dd611e227061fceba7ddc6a27 0.600000000000 1569400 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": 1094295, "vin": [ { "gen": { "height": 1094285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b114df0341f8b6a3e930a3a55592d898bcd8309dd611e227061fceba7ddc6a27" } } ], "extra": [ 1, 191, 147, 8, 52, 21, 22, 4, 43, 216, 242, 221, 19, 212, 171, 147, 255, 165, 207, 44, 116, 212, 18, 188, 224, 85, 38, 226, 188, 171, 127, 157, 231, 2, 17, 0, 0, 0, 7, 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