Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb8849224c411810b4e4493354cc3e18dc27b36a7150514cdfd9c545d6a24ba4

Tx prefix hash: b8b659bb8b314ba055cf0ed8d736d3b6155312a165012cc781344f21f14cdab9
Tx public key: 1ce36f4c0d6f1753a46afa8f270212bc89606d6ffde0aa458c9b6620a5ef5d48
Timestamp: 1672547414 Timestamp [UCT]: 2023-01-01 04:30:14 Age [y:d:h:m:s]: 02:075:18:03:14
Block: 665010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 575842 RingCT/type: yes/0
Extra: 011ce36f4c0d6f1753a46afa8f270212bc89606d6ffde0aa458c9b6620a5ef5d4802110000000133af99f4000000000000000000

1 output(s) for total of 3.841897516000 dcy

stealth address amount amount idx
00: 0bd6a7f2f7fe34a9885c628ab9e6148f7f81a5f5f160932b6cadae847d0f8d71 3.841897516000 1106025 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": 665020, "vin": [ { "gen": { "height": 665010 } } ], "vout": [ { "amount": 3841897516, "target": { "key": "0bd6a7f2f7fe34a9885c628ab9e6148f7f81a5f5f160932b6cadae847d0f8d71" } } ], "extra": [ 1, 28, 227, 111, 76, 13, 111, 23, 83, 164, 106, 250, 143, 39, 2, 18, 188, 137, 96, 109, 111, 253, 224, 170, 69, 140, 155, 102, 32, 165, 239, 93, 72, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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