Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ea06dbda28588136b3f8beb417433cd6e39d729a7b5369b53e6edb1bd9ab301

Tx prefix hash: 9c219e681e39f95d62b46ba70a2ebbf62ef2dd9c43ec07d05bf6e7fd6601ac3c
Tx public key: 45370c37b5802fd86ad868a1e5dff6a1e3b21f3375339ca94066b887f2242821
Timestamp: 1730175180 Timestamp [UCT]: 2024-10-29 04:13:00 Age [y:d:h:m:s]: 00:141:23:26:21
Block: 1141860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101296 RingCT/type: yes/0
Extra: 0145370c37b5802fd86ad868a1e5dff6a1e3b21f3375339ca94066b887f22428210211000000013cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5da4c893b8da7fef5a25b3d36c4d694ca9aa328ccea3b36ccf87635011be9e63 0.600000000000 1625691 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": 1141870, "vin": [ { "gen": { "height": 1141860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5da4c893b8da7fef5a25b3d36c4d694ca9aa328ccea3b36ccf87635011be9e63" } } ], "extra": [ 1, 69, 55, 12, 55, 181, 128, 47, 216, 106, 216, 104, 161, 229, 223, 246, 161, 227, 178, 31, 51, 117, 51, 156, 169, 64, 102, 184, 135, 242, 36, 40, 33, 2, 17, 0, 0, 0, 1, 60, 208, 252, 6, 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